Systems, computer program products, and methods for generating custom web pages for mobile device

ABSTRACT

A system generating a web page portal customized for a particular requesting mobile device is disclosed. The system includes an information store having multiple groups, each associated with device qualifications, web-design characteristics, and device identifications. The system also includes a custom web page development database (CWDD) including a plurality of web page component modules storing forms of web page components, and a custom web page development server (CWDS). The CWDS (i) receives an incoming request for a web page from the particular requesting mobile device, (ii) identifies a device type, and (iv) determines an applicable group. The CWDS also (v) obtains web-design characteristics from the applicable group, (vi) accesses the CWDD and obtains applicable web page components based on the web-design characteristics obtained from the applicable group of the information store, and (vii) generates the custom web page portal using the applicable web page components obtained from the CWDD.

TECHNICAL FIELD

The present disclosure relates generally to systems, computer programproducts, and methods for generating web pages and, more particularly,to systems and methods for generating custom web pages for specificrequesting mobile devices.

BACKGROUND

There are hundreds of different models of mobile devices in the markettoday, with surely more to come. Most modern devices, such as smartphones, are enabled to access Internet web pages. Despite the advancesin mobile devices and the great variety amongst the mobile devices, webpages are still often generated in a one-size-fits-all configuration,and specifically for larger personal computers (PCs), such as desktops,laptops, and tablet PCs.

As a result, web pages very often display awkwardly on mobile devicesand are cumbersome for the users to navigate. In addition, because webpages are generated for more powerful computing devices, the amount ofdata in the pages is usually too high for efficient rendering on mobiledevices, which slows download, presentation, and webpage navigation. Andwith the high and increasing number of users accessing the Internet frommobile devices, the larger web pages can cause unwanted latency andbandwidth consumption in the wireless data network.

One approach for addressing the existing challenges is to create aseparate web site for each device on the market. Each of these websites, though, would need to be hosted on a different domain orsub-domain. Hosting individual web sites on separate domains for eachmobile device is prohibitively costly in numerous ways. For example,hosts would need to communicate (e.g., advertise) the various differentdomains to each of the respective mobile devices. And the mobile deviceusers need to learn, remember, or store in a web page server adevice-specific domain (e.g., hyptothetical domain,http://www.iphone.att.com) that is different than the top-level domainweb page (e.g., http://www.att.com) they visit via their PC. Also,device-specific domains lack the benefits of top level domains,including ease of use and branding. Further, hosting individual websites on separate domains for each type of mobile device requiressubstantial duplication, storage, and maintenance of content. Stillfurther, new web sites and domains will have to be created for each newtype of device entering the market.

According to another approach, a variation of the first, a host wouldbegin with a common web site hosted on a primary, top-level domain. Thehost would then forward the web page content to device-specific domains(e.g., http://www.iphone.att.com). This approach alleviates the need forhosts to advertise the numerous device-specific domains, and for mobiledevice users to remember the device-specific domain appropriate forthem. This approach, though, still has drawbacks including therequirement for duplication of content and the overhead of maintainingmultiple sites. Further, delay is introduced by the process offorwarding the web page.

According to yet another approach, fully formed web pages are convertedfor use by a requesting mobile device. This approach, though, requireshosting and caching of a complete version of the web site for each typeof mobile device. Also, this approach requires additional serverresources and delay in converting an entire page from the original formto the converted form. For example, new versions of content must becreated each time a conversion is needed, to suit the requesting device.Another drawback to this approach is that the frequently changingdynamic content may not be cached and thus adding significant delays indisplaying the page.

The requirements of the aforementioned approaches undesirably consumepersonal and computing resources and increase the ultimate cost ofproviding and receiving services. A robust solution without theaforementioned drawbacks is needed.

SUMMARY

The present disclosure relates to a system for generating a web pageportal customized for a particular requesting mobile device. The systemincludes an information store having a plurality of groups, each groupbeing associated with mobile-device qualifications, web-designcharacteristics, and identification information corresponding to one ormore types of mobile devices assigned to the group. The system alsoincludes a custom web page development database (CWDD) including aplurality of web page component modules storing various forms of webpage components, and a custom web page development server (CWDS) incommunication with the information store and the CWDD. The CWDS isconfigured to (i) receive an incoming request for a web page from theparticular requesting mobile device, (ii) identify a device typeassociated with the particular requesting mobile device, and (iv)determine an applicable group of the plurality of groups in theinformation store based on the device type of the particular requestingmobile device. The CWDS is also configured to (v) obtain web-designcharacteristics from the applicable group of the information store, (vi)access the CWDD and obtain applicable web page components from the webpage component modules based on the web-design characteristics obtainedfrom the applicable group of the information store, and (vii) generatethe custom web page portal using the applicable web page componentsobtained from the CWDD.

In another aspect, the present disclosure relates to a non-transitorycomputer-readable medium storing instructions that, when executed by aprocessor, cause the processor to perform steps including receiving anincoming request for a web page from a particular requesting mobiledevice and identifying a device type associated with the particularrequesting mobile device. The steps also include determining anapplicable group of a plurality of groups stored in an information storebased on the device type of the particular requesting mobile device,obtaining web-design characteristics from the applicable group of theinformation store, accessing a custom web page development database(CWDD) having web page component modules, obtaining applicable web pagecomponents from the web page component modules of the CWDD based on theweb-design characteristics obtained from the applicable group of theinformation store, and generating the custom web page portal using theapplicable web page components obtained from the CWDD.

In another aspect, the present disclosure relates to a method forgenerating a web page portal customized for a particular requestingmobile device. The method includes a custom web page development server(CWDS) receiving an incoming request for a web page from the particularrequesting mobile device and identifying a device type associated withthe particular requesting mobile device. The CWDS also determines anapplicable group of a plurality of groups stored in an information storebased on the device type of the particular requesting mobile device,obtains web-design characteristics from the applicable group of theinformation store, and accesses a custom web page development database(CWDD) having web page component modules. The CWDS further obtainsapplicable web page components from the web page component modules ofthe CWDD based on the web-design characteristics obtained from theapplicable group of the information store and generates the custom webpage portal using the applicable web page components obtained from theCWDD.

Other aspects of the present invention will be in part apparent and inpart pointed out hereinafter.

DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a schematic block diagram of an exemplary mobiledevice for use in accordance with embodiments of the present disclosure.

FIG. 2 illustrates an architecture for developing custom web pagestailored to characteristics and applicable rules for various types ofmobile devices, in accordance with an embodiment of the presentdisclosure.

FIG. 3 illustrates a customized web page development server of thearchitecture shown in FIG. 2, in accordance with an embodiment of thepresent disclosure.

FIG. 4 illustrates an information store of the architecture of FIG. 2,in accordance with an embodiment of the present disclosure

FIG. 5 illustrates a customized web page development database of thearchitecture shown in FIG. 2, in accordance with an embodiment of thepresent disclosure.

FIG. 6 illustrates an exemplary method for grouping mobile device typesin a web page customization information store, according to anembodiment of the present disclosure.

FIG. 7 illustrates an exemplary method for generating a web pagetailored to a requesting mobile device, according to an embodiment ofthe present disclosure.

DETAILED DESCRIPTION

As required, detailed embodiments of the present disclosure aredisclosed herein. The disclosed embodiments are merely examples that maybe embodied in various and alternative forms, and combinations thereof.As used herein, for example, “exemplary,” and similar terms, referexpansively to embodiments that serve as an illustration, specimen,model or pattern. The figures are not necessarily to scale and somefeatures may be exaggerated or minimized, such as to show details ofparticular components. In some instances, well-known components,systems, materials or methods have not been described in detail in orderto avoid obscuring the present disclosure. Therefore, specificstructural and functional details disclosed herein are not to beinterpreted as limiting, but merely as a basis for the claims and as arepresentative basis for teaching one skilled in the art to variouslyemploy the present disclosure.

While the description includes a general context of computer-executableinstructions, the present disclosure can also be implemented incombination with other program modules and/or as a combination ofhardware and software. The terms “application,” “program,” or variantsthereof, are used expansively herein to include routines, programmodules, components, data structures, algorithms, and the like.Applications and programs can be implemented on various systemconfigurations, including single-processor or multiprocessor systems,minicomputers, mainframe computers, personal computers, hand-heldcomputing devices, microprocessor-based, programmable consumerelectronics, combinations thereof, and the like.

The term “computer-readable media” and variants thereof, as used in thespecification and claims, refers to storage media. In some embodiments,storage media includes volatile and/or non-volatile, removable, and/ornon-removable media. For example, storage media includes random accessmemory (RAM), read-only memory (ROM), electrically erasable programmableread-only memory (EEPROM), solid state memory or other memorytechnology, CD ROM, DVD, or other optical disk storage, magnetic tape,magnetic disk storage or other magnetic storage devices, or any othermedium that can be used to store the desired information

I. OVERVIEW OF THE DISCLOSURE

In various embodiments, the present disclosure describes systems andmethods for developing a custom web page tailored for a particularmobile device, such as a particular type of smart phone, requesting thepage. The system includes an information store includes various groupsinto which mobile device types are grouped. The systems include a webpage development database housing components (e.g., raw materials) forincluding custom-designed in web pages.

The system also includes a custom web page development server, whichreceives a web page request from a particular mobile device, accessesthe information store to obtain web page characteristics appropriate forthe group to which the requesting device is assigned, and constructs aweb page tailored to the particular requesting mobile device using theappropriate web page components from the web page development database.The web page development server may also consider rules or preferencesof the system, a communications service provider, and/or the device userin developing the custom web page, as described in greater detailherein.

The system is, thus, aware of the type of mobile device accessing it andthe needs of the device based on its characteristics and any applicableother rules. As such, the system is said to be device-aware, oraccess-aware.

The present system can be said to recharacterize the web page requestreceived from the particular mobile device. That is, the custom web pagedevelopment server, in procuring custom web page characteristicsspecific to the group in the information store to which the particularrequesting mobile device is assigned, essentially recharacterizes thegeneric request for a web page from the mobile device to require anoptimal page for the particular type of device.

The custom-designed web page can be a web portal in the traditionalsense, and also in a sense of being an amalgamation of componentsselected from the custom web page development database. With at leastthe latter perspective, each web page developed according to the presentdisclosure can be referred to as a type of web portal page.

II. MOBILE DEVICES

The various mobile devices available on the market differ in numerousways, including screen size, screen shape, layout of keyboard/screeninput, browser, and applications (e.g., navigation). The devices alsohave various other device capabilities and characteristics, such asprocessor speeds, and RAM capacity.

Turning to the figures, and more particularly to the first figure, FIG.1 illustrates a schematic block diagram of an exemplary mobile device100 for use in accordance with embodiments of the present disclosure.The mobile device 100 may be, for example, a smart phone, other Internetor web-browing-enabled phone, or dedicated navigation device.

Although connections are not shown between all of the componentsillustrated in FIG. 1, the components interact with each other to carryout device functions. In some embodiments, for example, the componentsare arranged so as to communicate via one or more busses (not shown). Itshould be understood that FIG. 1 and the following description areintended to provide a general understanding of a suitable environment inwhich the various aspects of some embodiments of the present disclosurecan be implemented.

In some embodiments, the mobile device 100 is a multimode headset andhas a variety of computer readable media, including, for example,volatile media, non-volatile media, removable media, and non-removablemedia. The term “computer-readable media” and variants thereof, as usedin the specification and claims, refers to storage media. In someembodiments, storage media includes volatile and/or non-volatile,removable, and/or non-removable media. For example, storage mediaincludes random access memory (RAM), read-only memory (ROM),electrically erasable programmable read-only memory (EEPROM), solidstate memory or other memory technology, CD ROM, DVD, or other opticaldisk storage, magnetic tape, magnetic disk storage or other magneticstorage devices, or any other medium that can be used to store thedesired information and that can be accessed by the mobile device 100.

As illustrated in FIG. 1, the mobile device 100 includes a display 102for displaying multimedia such as, for example, application graphicaluser interfaces (GUIs), text, images, video, telephony functions such asCaller ID data, setup functions, menus, music, metadata, messages,wallpaper, graphics, Internet content, device status, preferencessettings, map and location data, routes and other directions, points ofinterest (POI), and the like. The illustrated mobile device 100 alsoincludes a processor 104 for controlling, processing data, and/orexecuting computer-executable instructions of one or more applications,and a memory 106 for storing data and/or one or more applications 108.In some embodiments, the memory 106 stores information associated withdetermining location of the mobile device 100 according the methodsdescribed herein. For example, the memory 106 may store informationincluding user preference factors and/or administrative factors set byan administrator, manufacturer, or service provider, which are describedin more detail below.

In some embodiments, the application(s) 108 include a user interface(UI) application 110. The UI application 110 interfaces with a client112 (e.g., an operating system (OS)) to facilitate user interaction withdevice functionality and data. In some embodiments, the client 112 isone of Symbian OS® (Symbian OS is a registered trademark of SymbianLimited, of London, England), Microsoft® Windows® Mobile OS (Microsoftand Windows are registered trademarks of the Microsoft Corporation ofRedmond, Wash.), Palm webOS® (Palm WebOS is a registered trademark ofthe Palm Trademark Holding Company, of Sunnyvale, Calif.), Palm OS®(also a registered trademark of the Palm Trademark Holding Company),RIM° BlackBerry® OS (RIM and Blackberry are registered trademarks ofResearch In Motion Limited of Waterloo, Ontario, Canada), Apple® iPhone®OS (Apple and iPhone are registered trademarks of the Apple Corporation,of Cupertino, Calif.), or Google Android® OS (Android is a registeredtrademark of Google, Inc., of Mountain View, Calif.). These operatingsystems are merely exemplary of the operating systems that can be usedin accordance with the embodiments disclosed herein. Other operatingsystems are contemplated.

The UI application 110 aids the user in entering message content,viewing received messages, answering/initiating calls, entering/deletingdata, entering and setting user IDs and passwords, configuring settings,manipulating address book content and/or settings, interacting withother applications 114, and the like. In some embodiments, the otherapplications 114 include, for example, add-ons, plug-ins, locationapplications, e-mail applications, music applications, videoapplications, camera applications, power conservation applications, gameapplications, productivity applications, entertainment applications,enterprise applications, customer information management applications,accounting applications, authentication applications, applications,proprietary business applications, combinations thereof, and the like.The applications 108 are stored in the memory 106 and/or in a firmware116, and can be executed by the processor 104. The firmware 116 can alsostore code for execution during device 100 power up, for example.

The illustrated mobile device 100 also includes an input/output (I/O)interface 118 for input/output of data, such as, for example,identification of web pages, browsing actions such as link selection. Insome embodiments, the I/O interface 118 is a hardwire connection, suchas, for example, a USB, mini-USB, audio jack, PS2, IEEE 1394, serial,parallel, Ethernet (RJ48) port, RJ11 port, or the like. In someembodiments, the I/O interface 118 accepts other 110 devices such as,for example, keyboards, keypads, mice, interface tethers, stylus pens,printers, thumb drives, touch screens, multi-touch screens, touch pads,trackballs, joysticks, microphones, remote control devices, monitors,displays, liquid crystal displays (LCDs), combinations thereof, and thelike. It should be appreciated that the I/O interface 118 can be usedfor communications between the mobile device 100 and a network or localdevice, instead of, or in addition to, a communications component 120.

The communications component 120 interfaces with the processor 104 tofacilitate wired/wireless communications with external systems. Exampleexternal systems include, but are not limited to, intranets, networkdatabases, network storage systems, cellular networks, location systems,Voice over Internet Protocol (VoIP) networks, local area networks(LANs), wide area networks (WANs), metropolitan area networks (MANs),personal area networks (PANs), and other networks. In some embodiments,the external systems are implemented using WI-FI®, WIMAX®, combinationsand/or improvements thereof, and the like (WI-FI is a registeredtrademark of Wi-Fi Alliance, of Austin, Tex.; WIMAX is a registeredtrademark of WiMax Forum, of Mountain View, Calif.). In someembodiments, the communications component 120 includes a multimodecommunications subsystem for providing cellular communications viadifferent cellular technologies. In some embodiments, for example, afirst cellular transceiver 122 operates in one mode, such as, GlobalSystem for Mobile communications (GSM), and an Nth cellular transceiver124 operates in a different mode, such as Universal MobileTelecommunications System (UMTS). While only two cellular transceivers122, 124 are illustrated, the mobile device 100 may include more thantwo transceivers.

The illustrated communications component 120 also includes a transceiver126 for use by other communications technologies such as, for example,WIFI, WIMAX, BLUETOOTH®, infrared, infrared data association (IRDA),near field communications (NFC), RF, and the like (BLUETOOTH is aregistered trademark of Bluetooth SIG, Inc., of Bellevue, Wash.). Insome embodiments, the communications component 120 also facilitatereception from terrestrial radio networks, digital satellite radionetworks, Internet-based radio services networks, combinations thereof,and the like. The communications component 120 can process data from anetwork such as, for example, the Internet, an intranet, a homebroadband network, a WIFI hotspot, and the like, via an ISP, DSLprovider, or broadband provider.

In some embodiments of the present invention, audio capabilities for themobile device 100 are provided by an audio I/O component 128 including aspeaker to output audio signals and a microphone to receive audiosignals.

The illustrated mobile device 100 also includes a slot interface 130 foraccommodating a subscriber identity system 132 such as, for example, asubscriber identity module (SIM) card, a universal SIM (USW) card, or auniversal integrated circuit card (UICC). Alternatively, the subscriberidentity system 132 can be manufactured into the device 100, therebyobviating the need for a slot interface 130. In some embodiments, thesubscriber identity system 132 stores information associated withdetermining location of the mobile device 100 according the methodsdescribed herein. For example, the subscriber identity system 132 maystore information including user preference factors and/oradministrative factors set by an administrator, manufacturer, or serviceprovider, which are described in more detail below. In some embodiments,the subscriber identity system 132 is programmed by a manufacturer, aretailer, a user, a computer, a network operator, or the like.

The illustrated mobile device 100 also includes an image capture andprocessing system 134 (image system). Photos can be obtained via anassociated image capture subsystem of the image system 134, for example,a camera. The illustrated mobile device 100 also includes a video system136 for capturing, processing, recording, modifying, and/or transmittingvideo content.

The illustrated mobile device 100 also includes a power source 138, suchas batteries and/or other power subsystem (AC or DC). The power source138 can interface with an external power system or charging equipmentvia a power I/O component 139.

The illustrated mobile device 100 also includes a location component 140for use in determining geographic location of the mobile device 100. Thelocation component 142 may include, for example, a Global Positioning(GPS) unit including a GPS receiver.

III. CUSTOMIZED WEB PAGE DEVELOPMENT ARCHITECTURE

Turning to the next figure, FIG. 2 illustrates a customized web pagedevelopment architecture 200 for custom-designing web pages specific tocharacteristics and any applicable rules for various types of mobiledevices, according to an embodiment of the present disclosure. Thecustomized web page development architecture 200 includes a customizedweb page development server (CWDS) 202 and a customized web pagedevelopment database (CWDD) 204 associated with the CWDS 202. The CWDS202 is in some embodiments a dynamic web server such as a server basedon the Active Server Pages (ASP) web application framework (e.g.,ASP.net), the Java Server Pages (JSP) framework, the C++ scriptinglanguage, or other languages.

As described in more detail below, the CWDS 202 in some embodiments (a)receives a request for a web page from a particular mobile device 100via one or more communication networks 206 (e.g., cellular, WIFI), (b)identifies a type of the requesting mobile device 100 (e.g., amongsttypes 100 ₁, 100 _(ii), . . . , 100 _(N), where N is a positiveinteger), (c) identifies which of a plurality of pre-constructed devicegroups the mobile device 100 belongs to, (d) identifies groupcharacteristics, (e) accesses component storage modules of the CWDD 204,(f) selects appropriate web page components (i.e., web page rawmaterials) from the storage modules based on the identified mobiledevice group and its characteristics, (g) constructs a web page usingthe selected components from the component storage modules, and (h)delivers the web page to the particular requesting mobile device 100 viathe communication network(s) 206.

In some embodiments, the CWDS 202, in (f) selecting appropriate web pagecomponents from the component storage modules based on the identifiedmobile device group, also (f′) considers one or more device/usercharacteristics related to the mobile device 100, to the device user,and/or to an account for the user or device, such as operationalcharacteristics. These device/user characteristics can include, asprovided in more detail below, a present location of the mobile device100, preferences on account for the user, and preferences presented inthe process of procuring the web page by the user. For example, thecommunications service provider may establish rules affecting contentdistribution or page layout based on whether the particular requestingmobile device is in an area serviced by a service provider or isroaming.

As also described further below, the CWDS 202, in (f) selectingappropriate web page components from the component storage modules basedon the identified mobile device group, also (f″) considers one or moresystem characteristics, preferences, or rules (collectively, rules,herein for ease of explanation) associated with the host operating theCWDS 202 and/or preferences or rules associated with service provider.In some embodiments, the service provider hosts the CWDS 202. In otherembodiments, the web page owner hosts the CWDS 202.

As provided in more detail below, these system rules in some embodimentsrelate to one or more types of wireless networks being used by themobile device 100 to access the CWDS 202 (e.g., cellular, WIFI, WIMAX,etc.), time of day of the request, network data traffic history and/orat the time of the request, and services or limitations applicable tomobile devices 100 _(1-N) of the identified type, in general, or to theparticular requesting mobile device 100 _(N). Rules related to these andother variables can be established to assist the CWDS 202 host orservice provider in controlling bandwidth being used to satisfy Internetdata requests, while continuing to provide the customer with a desiredexperience.

As another example, service provider in some embodiments has establishedvarious formats of data accessible by the CWDS 200. In theseembodiments, the users of mobile devices can elect amongst the formatsfor controlling the amount and/or cost of the data they receive. Forinstance, for a higher cost, a user could elect a more data-intenseformat, in which case the CWDS 202 would include more data in web pagestailored for the user's device, or could elect a less data-intenseformat, in which case the CWDS 202 would include more less in web pagestailored for the user's device.

In another contemplated embodiment, the rules include a triggerassociated with a preset limit of data usage for the user. In aparticular embodiment, the CWDS 202 provides more data-intense web pages(e.g., more data regarding one or more types of content) until the CWDS202 determines that the trigger has been met, after which the CWDS 202provides less data-intense web pages according to the rule.

In one embodiment, the CWDS 202 is configured to present users of mobiledevices with an option for higher-data or lower-data web pages. Theoption may simply be between high and low, or levels on a graduatedscale, such as by allowing election of a particular level (e.g., on ascale of 1 to 5, or 1 to 10, etc.). This option can be presented at anytime, such as during an original initialization of the device, during aninitiation period for data service, or on the fly in response to a webpage request.

IV. CUSTOMIZED WEB PAGE DEVELOPMENT SERVER

FIG. 3 illustrates the CWDS 202 in more detail according to anembodiment of the present disclosure. The CWDS 202 includes at least oneCWDS memory 302 and at least one processor 304 in communication with theCWDS memory 302 via a data bus 306. The CWDS memory 302 includes one ormore storage modules storing computer-readable instructions executableby the processor 304 to perform the functions of the CWDS 202 describedherein. The CWDD 204 may be separate from and connected to the CWDS 202,or a part of the CWDS 202, such as by being a module of the CWDS memory302. The CWDS 202 also includes a network interface 308 by which theCWDS 202 communicates via the data bus 306 with the communicationnetwork 206.

V. MOBILE DEVICE INFORMATION STORE

FIG. 4 illustrates a mobile device information store 400, in accordancewith an embodiment of the present disclosure. As an example, theinformation store 400 in some embodiments is a file-based informationstore. The CWDS 202 is in communication with the information store 400for accessing select information in the information store 400 fordeveloping web pages customized for mobile devices 100 _(1-N) having atype identified in the store 400.

In one embodiment, the information store 400 is a part of the CWDD 204,and in another embodiment, it is a part of the CWDS memory 302. In oneembodiment, the information store 400 includes a portion positioned inthe CWDD 204 and another portion positioned in the CWDS memory 302.

The information store 400 identifies various groups in which mobiledevices 100 _(1-N) are categorized, along with information specific toeach group. In the figures, the various groups are listed forexplanatory purposes as GROUP A, GROUP B, etc., and the various stylesof mobile devices 100 _(1-N) are shown as Device type 1, Device type 2,etc. The groups and devices may be recognized by the CWDS 202 in any ofa variety of ways, such as by a separate identification code (not shown)for each group and for each device type. Each device, for instance, maybe represented by a device identifier, as provided further in thefollowing paragraph. The number of groups, and devices per group, areshown in FIG. 4 for purpose of illustration. The information store 400may include any number of groups and each group may include any numberof device types, including one.

The aforesaid instructions for execution by the CWDS 202 include thoseenabling the CWDS 202 to identify an incoming request for a web pagewith the type of device. The device type of device is used by the CWDS202 to identify the applicable group for procuring applicablecharacteristics from the information store 400. In one embodiment, groupmembership identification information is stored in the storage mediumholding the information store 400, and in a particular embodiment storedas part of the information store 400, as shown for example by referencenumeral 402 _(F) in the zoomed field of FIG. 4 in connection with GROUPF. The identification information 402 are in other embodiments stored inanother storage medium of the custom web page development architecture200. In one embodiment, the CWDS 202 identifies requesting devices by auser-agent property of a browser of the particular requesting mobiledevice identified in an incoming request message, such as in a header ofan HTTP (Hypertext Transfer Protocol) message.

The mobile device types, in some embodiments, correspond with a mobiledevice model. For example, device types may include the iPhone®, theBlackberry Curve®, the Blackberry Torch, and other devices (iPhone isregistered trademark of Apple, Inc., of Cupertino, Calif.; Blackberryand Blackberry Curve are registered trademarks of Research In Motion,Ltd., of Waterloo Canada).

The custom web page design architecture 200 includes qualificationinformation for use by the CWDS 202 in assigning a device type to agroup. In one embodiment, the qualification instructions are stored inthe storage media housing the information store 400, and in a particularembodiment, stored as part of the information store 400, as shown forexample by reference numeral 404 _(F) in the zoomed field of FIG. 4 inconnection with GROUP F. The qualification information 404 includesqualifying (e.g., required) device characteristics for the group, whichin some scenarios includes one or more ranges of characteristics that adevice must have or fall into to be classified in the group. In anotherembodiment, the group qualifications 404 are housed in the CWDS memory302 for use by the CWDS 202 in assigning a mobile device to a group ofthe information store 400.

Grouping devices provides efficiencies to the custom web page generationprocess by reducing development and maintenance of separate web pagedevelopment characteristics for each mobile device, especially separateweb page development characteristics for types of mobile devices thatare significantly similar. On the other hand, by requiring a higherlevel of similarity for mobile devices to be grouped, thus likelyresulting in more groups, and generally less mobile devices per group,web pages could be more-accurately tailored to the requesting mobiledevice 100 _(N). As required levels of similarity for grouping areincreased, the information store 400 approaches an embodiment of thepresent disclosure in which each device is essentially its own group.

The information store is, in various embodiments, designed or updated,such as by a designer and/or a component of the present architecture 200(e.g., CWDS 202) to set group qualifications to achieve a desiredbalance between higher efficiencies obtainable from more grouping andhigher web-page customization obtainable from less grouping.

Group qualifications and/or mobile device characteristics can berepresented in a variety of ways, such as by a numeric valuecorresponding to a screen size, a numeric value corresponding to screenshape, a binary representation of whether the device has or does nothave a particular quality, etc. In one contemplated embodiment, thequalifications for a group are represented by a combination of factorsincluding any of the mobile device characteristics described herein,such as screen size, screen shape, screen resolution, browsercapabilities, navigation capabilities, input mechanism (e.g., keyboard,touch pad, scroll wheel, roll ball, mouse, joystick, directional pad,analog stick, or touch screen), and other device capabilities.

In a particular contemplated embodiment, some or all of the variousfactors are weighted and combined to form a qualification. For instance,the qualification may be configured so that a close correlation indevice screen size weighs more than a close correlation in anothercharacteristic of devices, such as device scrolling mechanism (e.g.,screen-touch gesture, scroll button(s), roller ball, etc.) indetermining whether a mobile device qualifies for a certain group.

Primary features of the information store 400 are web page developmentcharacteristics, including group-specific web page developmentcharacteristics. Particularly, each group represented in the informationstore 400 includes corresponding group-specific web page developmentcharacteristics, as shown for example by 406 _(F) in the zoomed field ofthe GROUP F in FIG. 4. In one contemplated embodiment, the web pagedevelopment characteristics 406 include device-specific web pagedevelopment characteristics 406 for consideration by the CWDS 202 indeveloping custom web pages. By executing device-specific web pagedevelopment characteristics 406, the CWDS 202 can develop differentcustom web pages for devices of the same group (e.g., Device Types 1 and11 of GROUP F).

The web page development characteristics 406 include group-specific, andin some embodiments, device-specific, factors used by the CWDS 202 whenaccessing the CWDD 204 to create a customized web page for a particularrequesting mobile device 100. One exemplary web page developmentcharacteristic 406 is Java Script, as shown in the zoomed field of FIG.4 in connection with GROUP F.

Another exemplary web page development characteristic 406 is Web StyleSheet, as shown in the zoomed field of FIG. 4, Web Style Sheetsrepresent one way to define separation of presentation and content forweb pages using a markup language (e.g., Hypertext Markup Language(HTML), or Extensible HTML (XHTML)). Another exemplary web pagedevelopment characteristic 406 is Server Configuration Files, as alsoshown in FIG. 4.

Another exemplary web page development characteristic 406 is PreferredContent, as shown in the zoomed field of FIG. 4. Preferred Contentincludes rules for use by the CWDS 202 in selecting amongst varioustypes and/or levels of content available for the web page beingdeveloped. The types of content in some embodiments include text, image,video, and documents (as shown in connection with web page componentstorage modules 502 ₅, 502 ₇, and 502 ₉ in the FIG. 5 view of the CWDD202). Selection and presentation of web-page content based on web pagedevelopment characteristics 406, such as preferred Content, is describedfurther below in connection with the method 700 illustrated in FIG. 7for custom-developing a device-specific web page.

By providing the framework for developing a custom web page for thedevices in the various groups, the information store 400 effectivelypresents templates, which act as a filter through which the CWDS 202generates the custom web pages.

The information store 400, in some embodiments, also includes additionalrules for use by the CWDS 202 in developing device-specific custom webpages. The rules may include, for example, one or more preferencesestablished by a host of the CWDS 202 or a communications serviceprovider, which, as mentioned above, may be the same entity. Preferencesmay be specific to one or more groups, or, as mentioned above regardingweb page development characteristics 406, in general, particular to oneor more types of mobile devices. As an example, the additional rules mayinclude a preference established by the service provider that, for oneor more certain device groups or one or more particular devices, lowerlevels of select web-page content be provided, at least in an initialweb-page presented to a device, during peak hours of network operation(e.g., between 11:00 a.m. and 2:00 p.m.).

Other exemplary additional rules affecting content selection are basedon a speed of connection between the mobile device and the network, oron a location of the mobile device and the device type or group. Forexample, in some embodiments, the CWDS 202 delivers location-specificcontent to the particular requesting mobile device. Location-specificcontent in some embodiments includes content that may be, or is likelyto be, of interest to the user of the device based on their location,such as advertisements or coupons related to the location.

The rules considered by the CWDS 202 in some embodiments include rulesrelated to demographics of the users of mobile devices. In someparticular embodiments, the demographics are supplied by the usersand/or deducted based on device operation. Rules related to demographicsof a user can be referred to as a tag cloud. For instance, a user mayindicate that they are a graduate of a certain university and like acertain sport, the indications would become a part of a tag cloudassociated with the user. The rule in this case causes the CWDS 202 toinclude in the custom web page available content related to, forexample, an upcoming soccer match for the university. The rule couldalso relate to location, so that the content about the match ispresented to the user when the user is in a location near the match(e.g., on a Friday business trip, and perhaps otherwise unaware that heralma mater is playing nearby on Saturday morning).

The information store 400 is updated to include new devices added to themarketplace. A new device can be added to an existing group or a newgroup can be created for the new device, as appropriate, based at leastin part on a comparison between characteristics and capabilities of thenew device and qualifications of existing groups.

It is contemplated that the CWDS 202 will at times receive requests forweb pages from mobile devices that are not specifically assigned to agroup in the information store 400. In some embodiments, the informationstore includes a default, or catch-all group (not shown in detail)including default page-generation characteristics 406. The defaultpage-generation characteristics 406 can be configured, for example, toinclude average, median, and/or most common levels or values of web-pagecharacteristics to increase the likelihood that the page will betailored in ways most suitable for the unsupported device.

VI. CUSTOMIZED WEB PAGE DEVELOPMENT DATABASE

FIG. 5 illustrates the CWDD 204, of the architecture 200 shown in FIG.2, in accordance with an embodiment of the present disclosure. The CWDD204 includes a plurality of web page component storage modules 502 ₁,502 ₂, . . . , 502 _(M), where M is a positive integer. In oneembodiment, each storage module 502 holds multiple web page componentsof the same type. The CWDD 204 can be analogized to a warehousestructure, whereby components, or raw materials, for a product(customized web pages) are stored. More particularly, in someembodiments, the components are stored in component storage modules 502depending on the component types. Because separate components for theweb page are cached in the CWDD 204, and the CWDS 202 procures neededcomponents to generate the custom page, there is no need to cache anentire web page in its completed form.

The CWDS 202, for tailoring a web page most suitable for the mobiledevice, selectively accesses the component storage modules 502, procurescomponents therein, based on at least the type of mobile devicerequesting a web page. As mentioned above, and below in more detail, theCWDS 202 also considers variable such as characteristics associated withmobile device operation, the user of the particular requesting mobiledevice, the CWDS 202, utilized network(s), time of day, location of thedevice, network data traffic (historic and/or present), service formatoption (e.g., higher-data or lower-data plan election), and services orlimitations applicable to mobile devices of the identified type, ingeneral, or to the particular requesting mobile device.

Exemplary web page component storage modules 502 and the components theycan hold are now described, according to various embodiments of thepresent invention. A first content storage module 502 ₁ stores variousforms of Java Scripts. A second content storage module 502 ₂, storesvarious forms of Style Sheets. A third content storage module 502 ₃,stores various types of server configuration files.

Additional content storage modules 502 _(4-8, etc.) store various formsof content. Content may include, for example, any of text, HTML data,images, videos, and documents. For example, as shown in FIG. 5, a fourthcontent storage module 502 ₄, stores various forms of text, a fifthcontent storage module 502 ₅, stores various forms of images, a sixthcontent storage module 502 ₆, stores various forms of video, and aseventh content storage module 502 ₇, stores various forms of video.Other modules (e.g., 502 _(8,9, etc.)) store other types content.

VII. METHOD OF GROUPING DEVICES IN AN INFORMATION STORE

FIG. 6 shows an exemplary method 600 for grouping mobile device types ina web page customization information store 400, according to anembodiment of the present disclosure. It should be understood that thesteps of the method 600 are not necessarily presented in any particularorder and that performance of some or all the steps in an alternativeorder is possible and is contemplated. The steps have been presented inthe demonstrated order for ease of description and illustration. Stepscan be added, omitted and/or performed simultaneously without departingfrom the scope of the appended claims. It should also be understood thatthe illustrated method 600 can be ended at any time. In certainembodiments, some or all steps of this process, and/or substantiallyequivalent steps are performed by execution of computer-readableinstructions stored or included on a computer readable medium, such asthe memory 302 of the CWDS 202 and/or the CWDD 204, for example. Themethod 600 is performable by execution by the processor 304 of the CWDS202, as discussed primarily for explanation purposes, or anotherprocessor.

The method 600 begins and flow proceeds to step 602, whereat the CWDS202 defines membership qualifications (e.g., qualifications 404 _(F) inFIG. 4) for at least one group to be stored as part of the informationstore 400. At step 604, the CWDS 202 creates the group having thedefined qualifications. In various embodiments, the qualificationsinclude any combination of variables, such as a screen size, a screenshape, a screen resolution, browser capabilities, navigationcapabilities, input, and other device qualities. In one contemplatedembodiment, qualities of a particular device are used to define thegroup.

At step 604, the CWDS 202 also stores the qualifications 404 of thecreated group in the information store 400 in connection with the group.The qualifications 404 will be available for the CWDS 302 to referencewhen the CWDS 202 is considering adding device types in the future.

At step 606, the CWDS 202 identifies at least one type of device thatfits the qualifications 404 of the group. At step 608, the CWDS 202assigns the identified qualifying mobile device type to the createdgroup in the information store 400. For the contemplated embodiment inwhich qualities of a particular mobile device was used to define thegroup, that device is of course assigned to the group defined as such.At step 610, the CWDS 202 stores identifying information, such as auser-agent property of a browser of the type of device added to thecreated group. At step 612, the CWDS 202 defines and stores web pagedevelopment characteristics for the group. The CWDS 202 uses thesecharacteristics for developing custom web pages tailored to a requestingmobile device assigned to the created group, which development isfurther defined below in the method 700 illustrated in FIG. 7.

The method 600 can be repeated until all mobile devices available on themarket, or a subgroup of available devices, are assigned to one of thegroups. When a device is being evaluated for addition to the informationstore 400 and the device does not satisfactorily match an existinggroup, in some embodiments the CWDS 202 creates a new group toaccommodate the new device.

VIII. METHOD OF CUSTOM GENERATING A WEB PAGE FOR A MOBILE DEVICE

FIG. 7 shows an exemplary method 700 for developing a custom,device-specific, web page using the CWPD 202, according to an embodimentof the present disclosure. It should be understood that the steps of themethod 700 are not necessarily presented in any particular order andthat performance of some or all the steps in an alternative order ispossible and is contemplated. The steps have been presented in thedemonstrated order for ease of description and illustration. Steps canbe added, omitted and/or performed simultaneously without departing fromthe scope of the appended claims. It should also be understood that theillustrated method 700 can be ended at any time. In certain embodiments,some or all steps of this process, and/or substantially equivalent stepsare performed by execution of computer-readable instructions stored orincluded on a computer readable medium, such as the memory 302 of theCWDS 202 and/or the CWDD 204, for example.

The method 700 begins and flow proceeds to step 702, whereat the CWDS202 receives a request for a web page from a particular mobile device100 via one or more communication networks 206 (e.g., data,cellular)(see FIG. 2). The request may be in the form of, for example,an HTTP message.

At step 704, the CWDS 202 identifies a type of the mobile device 100,e.g., amongst types 1, 2, . . . , N, where N is a positive integer. Asdescribed above, in one embodiment, the CWDS identifies the device typeusing a user-agent property of the browser of the requesting device,which property can be identified, for example, in the incoming requestmessage, such as in a header of an HTTP request message.

At step 706, the CWDS 202 identifies which of a plurality ofpre-constructed device groups, of the information store 400 in FIG. 4,the mobile device 100 belongs to. At step 708, the CWDS 202 accesses theidentified group file of the information store 400 to procure custom webpage development characteristics particular to the group. Exemplarycustom web page development characteristics include Java Script, StyleSheet, Server Configuration Files, and content preferences, particularto the group of which the requesting device is a member.

The custom web page development characteristics identified in theinformation store 400 are those determined, e.g., in step 612 of themethod 600 described above in connection with FIG. 6, to be mostsuitable for requesting devices of the group. As described above, a mostsuitable page for the particular device, may use a particular JavaScript, a particular Style Sheet, particular Server Configuration Files,and particular content, as identified in the information store 400 inconnection with the group to which the requesting mobile device isassigned.

For example, the characteristics in the information store 400 for thegroup to which the particular requesting device is assigned may call forthe CWDS 202 to obtain, from the CWDD 204, a web article headline ofonly seven or less words. A longer version of the same headline may beprovided to requesting mobile devices of another group of theinformation store 400, depending on the characteristics of the othergroup. The shorter text preference for the group to which the particularrequesting mobile device is assigned may have been determined (e.g., instep 612 of the method 600 described above in connection with FIG. 6),for instance, due to a relatively-small display screen for devices inthe particular group and/or other factors related to the devices in theparticular group, such as processor speed.

Or the characteristics in the information store 400 for the group towhich the particular requesting device is assigned may call for the CWDS202 to obtain, from the CWDD 204, only two or three headlinescorresponding to top web articles. A heavier version of the same articlesummary, including for example, five to ten headlines or more, may beprovided to requesting mobile devices of another group of theinformation store 400, depending on the characteristics of the othergroup.

Similarly, the characteristics in the information store 400 for theparticular group to which the particular requesting device is assignedmay call for the CWDS 202 to obtain a summary of a web article forinclusion in the web page for the device. A longer version, such as thefull article, may be provided to requesting mobile devices of anothergroup of the information store 400, depending on the characteristics ofthe other group.

As another example, the characteristics in the information store 400 forthe particular group to which the particular requesting device isassigned may call for the CWDS 202 to obtain a relatively-short version(e.g., clip or snippet) of a video, and/or less videos overall forinclusion in the web page for the device. A longer version of the samevideo and/or more videos overall may be provided to requesting mobiledevices of another group of the information store 400, depending on thecharacteristics of the other group. The preference for shorter and/orlower number of videos for the group to which the particular requestingmobile device is assigned may have been determined (e.g., in step 612 ofthe method 600) due, for instance, to a relatively-slow processing speedfor devices in the particular group and/or other factors related to thedevices in the particular group.

In some embodiments, some or all inclusions of limited information(e.g., text, images, and video) in the custom web page are accompaniedby an option (e.g., web link) for more information, such as a fulltitle, a longer or a full version of a video, etc. In this way, theparticular mobile device is presented with an initial web page that ismost conducive to rendering, presentation, and/or navigation on therequesting mobile device, and the user of the device has the option ofobtaining additional information as desired.

At step 710, the CWDS 202 identifies any other applicable rules forgenerating the custom web page for the particular requesting device. Theother rules may include, for example, rules established by a hostoperating the CWDS 202, and/or by a server provider.

These rules may include, for example, a rule to provide arelatively-limited version of some or all data (e.g., text, images,videos, or documents) if the request is being serviced during a timeperiod determined from historical data to be a peak period for datatraffic, or during a time period determine based on contemporary data tobe relatively-busy at present (e.g., busy beyond a threshold) for thenetwork.

As another example, the rules may identify web page components (e.g.,components of the CWDD 204) or include characteristics identifying webpage components, based on a type of wireless network through which theparticular requesting mobile device is requesting the web page. Forexample, the rule may require that the CWDS 202 provide relatively-smallpieces of content when the mobile device is communicating via a WIFInetwork, compared to a cellular network. These rules are describedfurther above.

It is contemplated that applicable rules may be stored in andretrievable from the CWDD 204 in connection with the particular devicetype and/or the particular group to which the particular requestingdevice is assigned. In some embodiments, the CWDS 202 obtains suchapplication rules in step 708.

At step 712, the CWDS 204 identifies any rules specific to therequesting device, such as preferences set by the user, a program forwhich the web page is being requested, the host of the CWDS 202, and/ora service provider. In one contemplated embodiment, the CWDS 202communicates with a Home Location Register (HLR) associated with thedevice to obtain information that the CWDS 202 uses in determining webpage components to procure from the CWDD 204 for the custom web page. Itis contemplated that these other applicable rules, as well, may bestored in and retrievable from the CWDD 204 in connection with theparticular device type or the particular group to which the particularrequesting device is assigned. Thus, in some embodiments, the CWDS 202obtains such application rules in step 708.

An exemplary rule for a user may include a preference to receive pageswithout delivery of audio automatically (i.e., without express requestfor audio) during business hours (e.g., 8:00 a.m. to 5:00 p.m.). Asanother example, a preference may require presentation of more-detailedcontent when the mobile device is requesting information from a firstlocation (e.g., a home city or area of the user), and presentation ofless-detailed content when the mobile device is requesting the page froma second location (e.g., a city other than the user's home city orarea). The location of the device may be determined in conventionalways, such as by using a GPS unit of the particular requesting mobiledevice, or a recent position stored at a HLR associated with theparticular device.

At step 714, the CWDS 202 accesses component storage modules 502 of theCWDD 204 to obtain select components (i.e., raw materials for web-pagedevelopment), based on the web page development characteristics andrules obtained in steps 708, 710, and 712, for developing the custom webpage. In some contemplated scenarios, the CWDD 204 will include only asingle component of a certain type and so there is no decision for theCWDS 202 with respect to that certain component. For example, the CWDD204 may include only one version of an image for inclusion in web pages,and so in one contemplated embodiment that image is included in its onlyform in every web page. In another contemplated embodiment, group ordevice characteristics, or applicable rules, require that, when there isonly one available version of the certain component, the CWDS 202 is toobtain either the only available version of the certain component, ornot obtain the version, for inclusion in the custom web site beingtailored for the requesting device.

As described above, in some embodiments, the information store 400includes a default group (not identified in detail) including defaultweb page-generation characteristics for use by the CWDS 202 when amobile device requesting the web page is not found in the existinggroups of the information store 400. In those embodiments, the CWDS 202at step 708, procures default web page characteristics from the defaultgroup and, at step 714, obtains default web page-generation componentsfrom the CWDD 204 corresponding to the default web page characteristics.As described, above, default page-generation characteristics are in someembodiments configured to include an average, a median, and/or mostcommon levels or values of web page characteristics to increase thelikelihood that the page will be tailored in ways most suitable for theunsupported device.

At step 716, the CWDS 202 constructs a custom web page tailored for theassigned requesting mobile device using the components procured from theCWDD 204, and any applicable identified rules or preferences, asdescribed above.

In some particular embodiments, pages are coded in either standard HTMLor a template particular to a web server system being utilized. Inparticular embodiments, web page generation is optimized when the pagesare designed with separations of content (data), markup tags (HTML), andvisual elements (Style-Sheets), and behavior (Java-Script). In someparticular embodiments, visual elements are defined in Style-Sheets andapplied to page layouts and modules.

In some embodiments, page layout is based on modular design so thatcontent selection criteria may be configured and applied easily. Pagelayout and modules are in some embodiments coded, for example, usingbasic HTML tags such as <div>, <label>, <a>, <img>, <Ii>, etc. Allinteractive and behavioral elements are defined, for example, usingapplicable Java Scripts. In some embodiments, the content preferablydoes not have embedded markup tags.

At step 718, the CWDS 202 delivers the custom-developed, mobiledevice-specific, web page to the mobile device 100 via the communicationnetwork(s) 206. As described above, the web page can be a web portal, intraditional sense, and also in a sense of being an amalgamation ofcomponents from the CWDD 204. With the latter understanding, each webpage developed according to the present disclosure is said to be a webportal page.

In one contemplated embodiment, the steps 704-716 (e.g., steps of steps708-716) are performed before step 702. In this way, the CWDS 202anticipates the request of step 702 and the customized web page isavailable for faster delivery to the eventually requesting device. Thisembodiment could be especially helpful when, for example, the CWDS 202is receiving or expecting to receive a large number of requests for aparticular page, from one or more types of mobile devices, such as inconnection with a high-profile news event occurring or expected tooccur.

V. CONCLUSIONS

The systems and methods of the present disclosure allow maintenance ofcustom web page components (i.e., raw web page materials) at a singledomain for development of mobile device-specific web pages. In this way,there is no need to develop multiple domains for various versions of thesame page, or domain forwarding, which requires extra resources andadditional page load time. Maintaining a single web page also saveshardware, allows a host to maintain a primary brand domain, and allowseasier maintenance of a web site.

Another potential benefit of the present systems and methods is that webserver functionality, new features and business logic are automaticallyavailable for inclusion in mobile device-specific web sites withoutrequiring additional development of multiple particular web pages. Also,generally the same personnel (e.g., development team, testing team, andsupport team) can develop and/or maintain the present system, usingexisting processes, which significantly reduces cost. Further, newdevelopment and features (e.g., web-page components (e.g., content))benefit the devices at no cost as they are implemented into new customweb page portals.

Without the need to store separate web pages, e.g., at separate domains,server platform functionalities such as security, caching, buffering,business reporting, page optimizations, error handling, business logiccan be maintained once and reused for each custom web page, and so notseparately maintained and performed.

And because the system can be implemented on one server, or a group ofthe same web servers, separate integrations are not required. When a newmobile device is available, corresponding information is added to theinformation store 400 and the CWDD 204, and separate hardware andservers are not required.

Various embodiments of the present disclosure are disclosed herein. Thedisclosed embodiments are merely examples that may be embodied invarious and alternative forms, and combinations thereof. As used herein,for example, “exemplary,” and similar terms, refer expansively toembodiments that serve as an illustration, specimen, model, or pattern.The figures are not necessarily to scale and some features may beexaggerated or minimized, such as to show details of particularcomponents. In some instances, well-known components, systems, materialsor methods have not been described in detail in order to avoid obscuringthe present disclosure. Therefore, specific structural and functionaldetails disclosed herein are not to be interpreted as limiting, butmerely as a basis for the claims and as a representative basis forteaching one skilled in the art.

The law does not require and it is economically prohibitive toillustrate and teach every possible embodiment of the present claims.Hence, the above-described embodiments are merely exemplaryillustrations of implementations set forth for a clear understanding ofthe principles of the disclosure. Variations, modifications, andcombinations may be made to the above-described embodiments withoutdeparting from the scope of the claims. All such variations,modifications, and combinations are included herein by the scope of thisdisclosure and the following claims.

What is claimed is:
 1. A system, comprising: an information storeincluding a plurality of groups, each group being associated withmobile-device qualifications, web-design characteristics, andidentification information corresponding to at least one type of mobiledevice assigned to the group, wherein the plurality of groups includes adefault group for use in connection with any requesting mobile devicethat is not assigned to another group of the plurality of groups; acustom web page development database including a plurality of web pagecomponent modules comprising various forms of web page components; and acustom web page development server in communication with the informationstore and the custom web page development database.
 2. The system ofclaim 1, wherein the custom web page development server comprises acomputer-readable medium having computer-executable instructions that,when executed by a processor, cause the processor to perform operationscomprising: receiving an incoming request for a web page from aparticular requesting mobile device; identifying a device typeassociated with the particular requesting mobile device; and determiningan applicable group of the plurality of groups in the information storebased on the device type of the particular requesting mobile device,wherein the determining comprises determining the default group when theparticular requesting device is not assigned to another group in theinformation store.
 3. The system of claim 2, wherein the operationsfurther comprise obtaining web-design characteristics from theapplicable group of the information store, wherein the obtainingcomprising obtaining the web-design characteristics of the default groupwhen the particular requesting device is not assigned to another groupin the information store.
 4. The system of claim 3, wherein theweb-design characteristics of the default group have averagecharacteristics levels in order to increase a likelihood that a web pageportal to be generated will be tailored in ways most suitable for anymobile device that is not assigned to another group of the plurality ofgroups.
 5. The system of claim 3, wherein: the operations furthercomprise accessing the custom web page development database andobtaining, based on the web-design characteristics obtained from theapplicable group of the information store, applicable web pagecomponents from the web page component modules; and the operations ofaccessing and obtaining the applicable web page components are performedbased on the web-design characteristics of the default group when theparticular requesting device is not assigned to another group in theinformation store.
 6. The system of claim 5, wherein the operationsfurther comprise obtaining a rule of at least one entity selected from agroup of entities consisting of: (i) an operator of the system; (ii) acommunications service provider; and (iii) a user of the particularrequesting mobile device.
 7. The system of claim 6, wherein thecomputer-executable instructions that, when executed by the processor,cause the processor to perform the operation of obtaining the rule of atleast one entity, cause the processor to obtain the rule being relatedto at least one variable selected from a group of variables consistingof: (1) time of day at which the request is received; (2) a location ofthe particular requesting mobile device; (3) a type of a network bywhich the particular requesting mobile device is making the request; and(4) demographic data specific to a user of the particular requestingmobile device.
 8. The system of claim 1, wherein the information storeis a part of the custom web page development database.
 9. A method,comprising: receiving, by a custom web page development server having aprocessor, an incoming request for a web page from a particularrequesting mobile device; identifying, by the custom web pagedevelopment server, a device type associated with the particularrequesting mobile device; and determining, by the custom web pagedevelopment server, an applicable group of a plurality of groups storedin an information store based on the device type of the particularrequesting mobile device, wherein the plurality of groups includes adefault group for use in connection with any requesting mobile devicethat is not assigned to another group of the plurality of groups, andthe determining comprises determining the default group when theparticular requesting device is not assigned to another group in theinformation store.
 10. The method of claim 9, further comprisingobtaining, by the custom web page development server, web-designcharacteristics from the applicable group of the information store,wherein the obtaining comprising obtaining the web-designcharacteristics of the default group when the particular requestingdevice is not assigned to another group in the information store. 11.The method of claim 10, wherein the web-design characteristics of thedefault group have average characteristics levels in order to increase alikelihood that a web page portal to be generated will be tailored inways most suitable for any mobile device that is not assigned to anothergroup of the plurality of groups.
 12. The method of claim 10, furthercomprising: accessing, by the custom web page development server, acustom web page development database having web page component modules,wherein the accessing, and obtaining the applicable web page components,are performed based on the web-design characteristics of the defaultgroup when the particular requesting device is not assigned to anothergroup in the information store; and obtaining, by the custom web pagedevelopment server, applicable web page components from the web pagecomponent modules of the custom web page development database based onthe web-design characteristics obtained from the applicable group of theinformation store.
 13. The method of claim 12, further comprisingobtaining, by the custom web page development server, a rule of at leastone entity selected from a group of entities consisting of: (i) anoperator of the server; (ii) a communications service provider; and(iii) a user of the particular requesting mobile device.
 14. The methodof claim 13, wherein obtaining, by custom web page development server,the rule of at least one entity selected from the group of entitiescomprises obtaining the rule being related to at least one variableselected from a group of variables consisting of: (1) time of day atwhich the request is received; (2) a location of the requesting mobiledevice; and (3) a type of a network by which the requesting mobiledevice is making the request; and (4) demographic data specific to auser of the particular requesting mobile device.
 15. A computer-readablestorage device comprising computer-executable instructions that, whenexecuted by a processor, cause the processor to perform operationscomprising: receiving an incoming request for a web page from aparticular requesting mobile device; identifying a device typeassociated with the particular requesting mobile device; and determiningan applicable group of a plurality of groups stored in an informationstore based on the device type of the particular requesting mobiledevice, wherein the plurality of groups includes a default group for usein connection with any requesting mobile device that is not assigned toanother group of the plurality of groups, and the determining comprisesdetermining the default group when the particular requesting device isnot assigned to another group in the information store.
 16. Thecomputer-readable storage device of claim 15, wherein: the operationsfurther comprise obtaining web-design characteristics from theapplicable group of the information store; and the obtaining comprisesobtaining the web-design characteristics of the default group when theparticular requesting device is not assigned to another group in theinformation store.
 17. The computer-readable storage device of claim 16,wherein the web-design characteristics of the default group have averagecharacteristics levels in order to increase a likelihood that a web pageportal to be generated will be tailored in ways most suitable for anymobile device that is not assigned to another group of the plurality ofgroups.
 18. The computer-readable storage device of claim 16, wherein:the operations further comprise accessing a custom web page developmentdatabase having web page component modules and obtaining applicable webpage components from the web page component modules of the custom webpage development database based on the web-design characteristicsobtained from the applicable group of the information store; and theoperations of accessing and obtaining the applicable web page componentsare performed based on the web-design characteristics of the defaultgroup when the particular requesting device is not assigned to anothergroup in the information store.
 19. The computer-readable storage deviceof claim 18, wherein the operations further comprise obtaining a rule ofat least one entity selected from a group of entities consisting of: (i)an operator of the computer-readable device; (ii) a communicationsservice provider; and (iii) a user of the particular requesting mobiledevice.
 20. The computer-readable storage device of claim 19, whereinthe operation of obtaining the rule of at least one entity selected fromthe group of entities comprises obtaining the rule being related to atleast one variable selected from a group of variables consisting of: (1)time of day at which the request is received; (2) a location of theparticular requesting mobile device; (3) a type of a network by whichthe particular requesting mobile device is making the request; and (4)demographic data specific to a user of the particular requesting mobiledevice.